Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Change license to Apache 2.0 #374

Merged
merged 4 commits into from
May 20, 2024

Conversation

mtrezza
Copy link
Member

@mtrezza mtrezza commented May 20, 2024

This removes obsolete Parse LLC references and changes the license to Apache 2.0 in line with other Pares Platform repos.

Note: This is a breaking change, not per functionality but legally.

Copy link

parse-github-assistant bot commented May 20, 2024

Thanks for opening this pull request!

  • ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

@mtrezza mtrezza added the state:breaking Breaking change requires major version increment and `BREAKING CHANGE` commit message label May 20, 2024
@mtrezza mtrezza merged commit 6887aff into parse-community:master May 20, 2024
2 checks passed
@mtrezza mtrezza deleted the docs/change-license branch May 20, 2024 21:37
parseplatformorg pushed a commit that referenced this pull request May 23, 2024
# [3.0.0](2.0.0...3.0.0) (2024-05-23)

### Features

* Change license to Apache 2.0 ([#374](#374)) ([6887aff](6887aff))

### BREAKING CHANGES

* This changes the license to Apache 2.0. This release may contain breaking changes which are not listed here, so please make sure to test your app carefully when upgrading. ([6887aff](6887aff))
@parseplatformorg
Copy link

🎉 This change has been released in version 3.0.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:breaking Breaking change requires major version increment and `BREAKING CHANGE` commit message state:released Released as stable version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants